home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Night Owl 19
/
Night Owl (The Best of Shareware)(NOPV 19)(1996).ISO
/
007a
/
bw310mx2.zip
/
README.1ST
< prev
next >
Wrap
Text File
|
1995-12-01
|
10KB
|
203 lines
The Blue Wave Mail Door Version 3.10
for Maximus Version 2.0x
Copyright (C) 1992-1995 by Cutting Edge Computing
All Rights Reserved
This short documentation file contains instructions for both NEW and
UPGRADE installations. Please read the appropriate section in this
document carefully before attempting to install the mail door. A "What's
New" section is included at the end of this file.
PLEASE NOTE THAT DAVE PARKER IS NO LONGER THE EUROPEAN REGISTRATION SITE.
Steve Stacher (2:443/888) has assumed the European registration site
position. Please see the form REGISTER.EUR for further information.
=====================================
USING THIS MAIL DOOR WITH MAXIMUS 3.0
=====================================
At the time this documentation was written (December 1, 1995), a mail door
which supports all Maximus 3.0 features was just entering the test period.
We hope to provide this mail door to Maximus SysOps in early January.
This version of The Blue Wave Mail Door can be run with a Maximus 3.0
system, but please be aware that it can only support features contained
in Maximus 2.02. Several tweaks have been made to the mail door to
account for slight differences between Maximus 2.x and 3.0.
In order to run the mail door with Maximus 3.0, you *must* run SILTP.EXE
(the Maximus control file compiler) with the -2s switch:
SILT max -2s
This will generate Maximus 2.x compatible AREA.DAT/AREA.NDX files, which
the mail door needs in order to function properly. After running SILTP,
you should then run the enclosed FIXSILTP.EXE. FixSilt will go through
your Max 2.x compatibility files and fix some things that SILTP 3.0 doesn't
do quite right. Each time you run SILTP, you should remember to run
FIXSILTP. By default, FixSilt will look for MAX.PRM in the current
directory. If MAX.PRM is not in the current directory, you must run
FixSilt in the following manner:
FIXSILTP BBS.PRM
FIXSILTP X:\MAX\MAX.PRM
If you are experiencing trouble with FidoNet-style AKA addresses not being
written to your messages properly (both in Origin lines and message
headers), you will need to use FIXSILTP.EXE.
If you are currently using some workaround to use the mail door in local
mode because you were getting the message "Unable to open USER. Aborting.",
you will no longer need to use this workaround.
=================
NEW INSTALLATIONS
=================
Please read Chapter 5 in BWMAIL.DOC for full installation instructions.
Sections 5.1 and 5.2 contain the quick step-by-step installation procedure.
Additionally, you will need to follow the directions in the previous
section if you are installing this mail door for use with Maximus 3.0.
=====================
UPGRADE INSTALLATIONS
=====================
The first step in performing this upgrade is to determine the version
number of the door that you are currently running. If you are currently
running version 3.00 or version 3.01, you can continue with the upgrade
procedures outlined below. If you are using a version of the mail door
earlier than version 3.00, an upgrade installation is not possible -- you
will need to install the mail door into an empty directory.
1) Locate the file 300to310.exe. This file should have been enclosed
in the main BW310MX2.ZIP archive. Copy this file to the directory
where your mail door is currently installed.
2) Get a directory listing of "*.PRM" in your Blue Wave Mail Door
directory. If the only *.PRM file listed is "BWMAIL.PRM", you will
only need to run the conversion program once. If your system is
configured with multiple door configuration files, you will need to run
the conversion program once for *each* .PRM file in the directory.
3) Run the program 300to310.exe -- this will upgrade your current data
files to be compatible with the new version of the mail door. You must
run this once for each mail door configuration file (see step #2).
If the data file conversion is successful, you may delete 300to310.exe.
This program is no longer needed.
4) Unpack the ENTIRE contents of BWMAIL.ZIP (enclosed within the
BW310MX2.ZIP archive) to your current mail door directory. The entire
contents of this archive need to be unpacked -- overwrite all files
with duplicate file names.
5) The following files should be deleted from your mail door directory,
as they are no longer used:
* BWMAIL.EXE (replaced with BWMAIL2.EXE)
* BWMAIL.OVR (replaced with BWMAIL2.OVR)
* BWUTILS.EXE (replaced with BWSETUP2.EXE)
* BWDOOR.USE (replaced with BWDOOR.DOC)
* BWAREAS.IDX (conversion program should have done this)
6) Change all menu commands and batch files that run BWMAIL.EXE to run
BWMAIL2.EXE. A change was made to the executable file name in order
to accomodate the (many) user requests to support both DOS and OS/2
executables in the same directory.
7) Check your BBS maintenance batch files for any instances of:
BWUTILS PURGE nn
This packs The Blue Wave Mail Door's user file, removing all users who
have not used the mail door in 'nn' days. All occurrences of this need
to be replaced with:
BWSETUP2 PURGE nn
If you do not currently remove old records from your mail door user
file, this would be a good time to add it!
8) If you have batch files that pack your mail in local mode, either in
an event or on demand, the /K<user#> command line switch for BWMAIL2
has changed.
You will want to change all occurrences of /K<user#> to /K<user_name>.
Please note that the user name must immediately follow the /K (no
spaces), and all spaces in the user name must be replaced with an
underscore.
Although /K<user#> is still supported, the <user#> is now 0-based. If
you are the SysOp, "BWMAIL /k1" used to load the first record out of
the user file. Now you would need to use "BWMAIL2 /k0".
It is recommended, however, that you use "BWMAIL2 /kjoe_sysop". The
Maximus 3.0 mail door (when available) will not support the /K<user#>
construct, as user numbers were removed in Maximus 3.0.
9) If you are running Maximus 3.0, please be sure to read the first
section of this file, USING THIS MAIL DOOR WITH MAXIMUS 3.0.
10) Run the new BWSETUP2 program to insure that the conversion completed
successfully. Please be sure to check out the new "FidoNet->Internet
Gateway" menu item in BWSETUP2. There is both online documentation
(press <F1> at any time while in BWSETUP) and standard documentation
(BWMAIL.DOC) for this new feature.
11) You must insure that you have a copy of MSGAPI32.DLL available for
this version of the mail door. It has been upgraded to use the
32-bit DLL provided with Maximus 3.0 and Squish 1.1x. This DLL
must be in a directory contained in your CONFIG.SYS LIBPATH statement.
==========
WHAT'S NEW
==========
*> BWSETUP now includes extensive online help. At any time while using
BWSETUP, press <F1> for context-sensitive help.
*> A new seamless FidoNet->Internet Gateway which allows users of The
Blue Wave Offline Mail Reader version 2.20 or higher (and third-party
readers that support the BW 3.0 Packet Specifications) the ability
to easily address/send Internet E-Mail messages through standard
FidoNet NetMail.
*> The mail door now supports offline configuration of the following
new items when used with a mail reader capable of creating BW 3.0
Packets:
* Extended Message Information (Seen-By, Control-A Lines)
* New File Listings
* Bundling Command Macros
* Auto-Executable Bundling Commands
* Numeric Packet Extensions
* Maximum Uncompressed Mail Packet Sizes
* Personal-Only Message Downloading in Specific Message Areas
* Personal and To: "All" Message Downloading in Message Areas
*> The mail door now includes an enhanced File Request mechanism, which
allows a user to download requested files at the same time they
download a mail packet. In order for this to work, the user must
enter the mail door in "Interactive" menu mode, and must first perform
a reply packet upload, followed by a mail packet download.
*> The mail door, when used with a BW 3.0 Packet compliant mail reader,
will now generate FidoNet ^aREPLY: kludge lines in EchoMail and NetMail
message areas.
*> Enhanced the mail door internal protocol module to consume less time
slices under multitaskers such as DESQview and Windows 3.1, and
operating systems such as OS/2 and Windows 95. Additionally, the
internal protocol module should yield much better transfer rates
with all operating systems and multitaskers.